Data Acquisition Idea Exchange

I am learning how to use the scripting feature of NI-RFSG and the script editor is an incredible frustrating tool.

Why do you show text if you can't type? Show a diagram if you don't want people typing.

I am using Notepad to type my scripts and then moving the text over.

There should be a way to allow people to type in the script editor and do on the fly syntax checking... or even do it after. I can export my script to the clipboard, but why can't I paste into it?

Just let people type.

The use of NI DAQmx Global Virtual Channels is the best way that I have found to configure and manage parameter scaling to provide measurement data directly in engineering units. The software architecture of our data acquisition applications is centered around the use of Global Channels (aka Virtual Channels). Configuring Global Channels using NI MAX (Measurement & Automation Explorer) is convenient for a small number of measurement channels. However, in system configurations with hundreds of channels, to create and manage them effectively, you need to build your own application for this task.  We have built custom Global Channel creation VIs in LabVIEW for each type of analog input or sensor type that we use. These VIs are designed to read a configuration table in CSV format, and then loop through creating a Global Channel for each table row of information.  This process allows for more flexibility in naming the channels as well as setting different scaling and storage of other channel-specific metadata.

We employ multiple networked data acquisition systems with Linux-based NI controllers, and we manage those DAQmx Global Channels across our network.  Currently, to create DAQmx Global Channels on these systems, we must directly connect to the NI controller in the LabVIEW Project View and run our suite of Global Channel creation apps on that particular controller using their accompanying, locally-stored CSV configuration file.  Currently, our networked distributed data acquisition system has grown to 10 controllers, each with their own set of common I/O.  The creation of those Global Channels has now become cumbersome because we have five I/O types to manage and hence five custom LabVIEW applications each with a specific configuration file to run on 10 controllers individually.

A potential simplification to the process would be to run our custom LabVIEW applications on a Windows host PC and create the DAQmx Global Channels remotely.  That would eliminate the need to directly connect to each controller from the LabVIEW Project View and copy a common set of config files to each controller and run the same applications on individually on each controller.  However, the current version of DAQmx makes no provision for remotely creating DAQmx Global Channels.  Note that NI-MAX is able to create DAQmx Global Channels remotely, but this functionality is not exposed for LabVIEW programmers to utilize.  My idea/suggestion is that NI make this functionality available in LabVIEW.

IMAQdx Timeout is a non settable property. It is fixed on 5s

When I do not trigger my camera for 5 seconds (and that is what I want regularly after aquisitions at 100FPS) , I get a timeout error.

Problem:  When creating large numbers of virtual channels, the calibraton of these channels can be very time consuming and cumbersome.  In large applications there can be literally hundreds of channels requiring days to calibrate. 

Calibration equipment these days can be purchased with programmable capability or remote communication.  Having low level functions available in Labview to calibrate MAX virtual channels programmatically would greatly reduce the time needed for calibration and reduce the potential errors of calibrating each point individually.  It would also be useful to view the calibration data and scaling data from MAX in the Labview environment.